Proximity detection in a device to device network

ABSTRACT

A technology for a user equipment (UE) that is operable to communicate in a device to device (D2D) network. A proximity detection request can be communicated to an evolved packet core (EPC). The proximity detection request can include a window parameter, an identification information of a second UE, and a proximity detection signal indicating whether the proximity detection request is for proximity detection of the second UE or for establishing a D2D connection with the second UE. A proximity alert message can be received from the EPC at the window parameter.

RELATED APPLICATIONS

This application claims the benefit of and hereby incorporates byreference U.S. Provisional Patent Application Ser. No. 61/809,157, filedApr. 5, 2013.

BACKGROUND

Device to device (D2D) wireless communication techniques may be used toperform peer-to-peer or point-to-point (P2P) communications or machinetype communications among mobile devices and networks in a variety ofsettings. D2D communications between mobile devices may be designed tocomplement the use of centralized communications from a wireless basestation, for example, centralized station-to-mobile communications froman evolved Node B (eNode B) in a carrier network.

D2D direct communications are limited to devices, such as user equipment(UE), located within a communication range of a wireless protocol ornetwork configuration. D2D direct communications are also limited when aselected device may not be aware of whether D2D communication-capabledevices are within communication range or known devices associated withD2D communication-capable devices are within communication range. D2Ddirect communications are also limited when a selected device may not beaware of whether the D2D communication-capable devices and/or knowndevices associated with D2D communication-capable devices are currentlyor prospectively in proximity to the device. Existing discoverytechniques used to locate and seek out nearby D2D-capable devicesgenerally involve the use of broadcasting and response schemes, whichutilize detailed processing, responses, and data exchanges to discoverdevices.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the disclosure will be apparent from thedetailed description which follows, taken in conjunction with theaccompanying drawings, which together illustrate, by way of example,features of the disclosure; and, wherein:

FIG. 1 depicts a multi-RAT HetNet with a macro-cell and a macro-nodeoverlaided with layers of lower power nodes in accordance with anexample;

FIG. 2 depicts a cooperative network in accordance with an example;

FIG. 3 illustrates a communications network for facilitating directdevice to device (D2D) communications through a communications networkin accordance with an example;

FIG. 4 shows a data sequence for establishing a network-assisted D2Dcommunications connection between a user equipment (UE) and another UEwhen the other UE is in proximity to the UE in accordance with anexample;

FIG. 5 shows a data sequence for detecting proximity between a UE andanother UE based on a proximity detection request in accordance with anexample;

FIG. 6 shows another data sequence for establishing a network-assistedD2D communications connection between a UE and another UE when a datewindow parameter occurs in accordance with an example;

FIG. 7 shows another data sequence for establishing a network-assistedD2D communications connection between a UE and another UE when alocation window parameter occurs in accordance with an example;

FIG. 8 depicts the functionality of the computer circuitry of a UEoperable to communicate in a D2D network in accordance with an example;

FIG. 9 depicts the functionality of the computer circuitry of an evolvedpacket core (EPC) that is operable to assist a UE to communicate in aD2D network in accordance with an example;

FIG. 10 illustrates a method for assisting UE to communicate in a D2Dnetwork in accordance with an example; and

FIG. 11 illustrates a diagram of a UE in accordance with an example.

Reference will now be made to the exemplary embodiments illustrated, andspecific language will be used herein to describe the same. It willnevertheless be understood that no limitation of the scope of theinvention is thereby intended.

DETAILED DESCRIPTION

Before the present invention is disclosed and described, it is to beunderstood that this invention is not limited to the particularstructures, process steps, or materials disclosed herein, but isextended to equivalents thereof as would be recognized by thoseordinarily skilled in the relevant arts. It should also be understoodthat terminology employed herein is used for the purpose of describingparticular examples only and is not intended to be limiting. The samereference numerals in different drawings represent the same element.Numbers provided in flow charts and processes are provided for clarityin illustrating steps and operations and do not necessarily indicate aparticular order or sequence.

In device to device (D2D) communications, multiple mobile wirelessdevices, such as user equipment (UEs), can be configured to directlycommunicate with each other. In one embodiment, D2D connections betweenUEs can be established by one or more devices manually scanning tolocate other nearby D2D-capable devices. In another embodiment, D2Dconnections between UEs can be established by broadcasting connectionavailability using a wireless network to locate nearby D2D-capabledevices. Manually scanning for other UEs or broadcasting connectionavailability can involve the UE constantly scanning for other UEs andcan cause a relatively high power usage at the UE. Additionally, evenupon discovery of a nearby D2D-capable UE, identification andauthentication issues can prevent establishment of a D2D connectionbetween devices.

FIG. 1 show an eNode B 110 in a network assisted D2D communicationssystem that includes a transceiver 120 and a computer processor 130.FIG. 1 also illustrates a UE 140 in the network assisted D2Dcommunications system that includes a transceiver 150 and a computerprocessor 160. D2D communication systems can provide mobile device userswith better quality of service (QoS), new applications, and increasedmobility support. To establish D2D communications, the UEs within a D2Dcommunications system can be configured to communicate with other D2Denabled UEs that are participating in the D2D system.

FIG. 2 illustrates UE A 220 and UE B 230 each in communication with aneNode B 210 of a communications network using communications links 212and 214. FIG. 2 also illustrates that UE A 220 and UE B 230 are indirect communication with each other using a D2D communications link222. The UEs in the D2D communication system can share resources of acommunications network, where the UEs are configured to share resourceswith devices that are communicating with the eNode B in thecommunications network. In one embodiment, the communications networkcan be a cellular network, such as a third generation partnershipproject (3GPP) long term evolution (LTE) Rel. 8, 9, 10, 11, or 12network and/or an Institute of Electrical and Electronics Engineers(IEEE) 802.16p, 802.16n, 802.16m-2011, 802.16h-2010, 802.16j-2009,802.16-2009 network.

The device discovery process can include a device discovery messagetransmitted from the communications network. The device discoverymessage can indicate to at least a pair of the UEs a device discoveryperiod. The device discovery period can be a discovery period for UEs todiscover each other and communicate with each other via the D2Dprotocols. One advantage of using a network assisted device discoveryprocess can be to improve the speed and power efficiency of the D2Ddevice discovery procedure for each UE in a D2D network.

In one embodiment, the network assisted D2D discovery can be used toperform network level device proximity detection. To perform proximitydetection, a core network device, such as a proximity services (ProSe)server, can use UE locations as inputs and determine a potential forsuccessful D2D communications for the UE. In one embodiment, for networklevel D2D discovery, a communications network can monitor UE locationsand calculate a proximity of one or more UEs to other UEs. In oneembodiment, location services (LCS) of the network can be used toestimate a UE location.

In one embodiment, a ProSe server can be a network entity, a networkelement, or a core network device that can assist UEs with proximitydetection. For example, the ProSe server can obtain UE locationestimates via the LCS of a network. Traditionally, LCS functionalitiescan expend a lot of signaling on a core network and radio and/or batteryresources at the UE to perform proximity detection.

In one embodiment, the network can assist in locating or discoveringvarious D2D-capable devices within a network and enable D2Dauthentication between the D2D-capable devices. Upon discovery and D2Dauthentication of proximate or adjacent D2D-capable devices, a D2Dcommunications link between the adjacent D2D devices can be establishedto facilitate the exchange of data over the D2D communications link. Inone embodiment, the D2D communications link can be deployed inconnection with selected date-based services or location-based services.In one embodiment, the D2D communications link can be established overan unlicensed band in a wireless network, such as a wireless local areanetwork (WLAN). In one embodiment, the WLAN can operate based on astandard such as the Institute of Electronics and Electrical Engineers(IEEE) 802.11-2012, IEEE 802.11ac, or IEEE 802.11ad standards. Inanother embodiment, the D2D communications link can be established overunlicensed portions of the radio spectrum, such as Bluetooth v1.0,Bluetooth v2.0, Bluetooth v3.0, Bluetooth v4.0, IEEE 802.15.4-2003(Zigbee 2003), IEEE 802.15.4-2006 (Zigbee 2006), IEEE 802.15.4-2007(Zigbee Pro). In another embodiment, the D2D communications link can beestablished over licensed bands in a cellular network. In oneembodiment, the cellular network may be 3GPP LTE Rel. 8, 9, 10, 11, or12 networks and/or IEEE 802.16p, 802.16n, 802.16m-2011, 802.16h-2010,802.16j-2009, 802.16-2009.

In one embodiment, network-assisted D2D discovery can use an eNode B oran evolved packet core (EPC) of an eNode B to discover and/or identifyother D2D enabled UEs and aid in the connection of the D2D UEs for D2Dcommunication of data. In one embodiment, a communications network, suchas a cellular third generation partnership project (3GPP) network, canassist the UEs in setting up D2D communications links with other UEsconfigured for D2D communications.

For example, a UE in communication with a cellular communicationsnetwork, such as a cellular radio access network (RAN), can request UEdiscovery assistance from an EPC of the communications network.Information obtained from the UE discovery assistance can includeinformation to assist the D2D connection discovery process and/oridentification information for other UEs. The EPC can also communicateauthentication information, security information, identificationinformation, and establish a time period to coordinate D2D discovery andconnection operations. In one embodiment, in a cellular networkenvironment, the EPC can maintain LCS to monitor an approximate locationof the various UEs in the communications network. The locationinformation of the UEs with respect to other UEs in the communicationsnetwork can assist the UEs in discovering other D2D-capable devicesand/or establishing D2D connections for direct communications.

FIG. 3 illustrates a communications network 300 for facilitating directD2D communications through the communications network 300. Within thecommunications network 300, a plurality of UEs, such as UE A 320 and UEB 330 are in communication with the EPC 318 through communications link316 via communications links 312 and 314 with the eNode B 310,respectively. FIG. 3 further illustrates that within the communicationsnetwork 300, a plurality of UEs, such as UE A 320 and UE B 330 can be inD2D communications with each other using a D2D communications link 322.In one embodiment, the communications network 300 can be a cellularnetwork or other type of wireless network. In one embodiment, a wirelessnetwork can enable a UE to communicate data or information via the eNodeB 310 to the EPC 318 of the communications network 300. In anotherembodiment, the cellular network can provide for the communication ofdata between the UE A 320 and the UE B 330 using a cellularcommunications links 312 and 314, respectively.

D2D communications between the UE A 320 and the UE B 330 can beperformed using D2D communications link 322. In one embodiment, the D2Dcommunications link 322 can be configured for direct point-to-pointconnections between devices. In another embodiment, the D2Dcommunications link 322 can be configured indirect peer-to-peerconnections between devices or multi-node connections between devices.

The D2D communications link 322 can be established with the assistanceof the EPC 318 of the communications network 300. The EPC 318 can assistthe UE A 320, in discovering an other D2D UE B 330 and setting up a D2Dcommunications link 322 between UE A 320 and D2D UE B 330.

In one embodiment, a proximity detection request received from a UE canbe used to indicate a request to an EPC to perform proximity detectionof other selected UEs based on a date window parameter and/or a locationwindow parameter. In one embodiment, the date window parameter canindicate a specific date that a UE requests for proximity detection fromthe network or the EPC. For example, the date window parameter canindicate one or more specific times of the day, days of the week, weeksof the month, months of the year, or other specific times for proximitydetection.

In another embodiment, the UE can designate a permanent detection windowfor specific locations. For example, the location window parameter canindicate a specific location that a UE requests that the EPC performproximity detection. For example, the location window parameter canindicate a specific enterprise location or commercial environment forproximity detection. In one embodiment, a window parameter can be acombination of the date window parameter and a location windowparameter. For example, the combination of the date window parameter andthe location window parameter can indicate a specific time of the dayand a specific location to perform proximity detection.

Typically, a device, such as a UE, is configured to continuously searchfor other D2D devices on radio bands when the device is configured toengage in D2D communications. One advantage of targeted network-assisteddevice discovery, such as for a selected date window parameter and/or alocation window parameter, can be to alleviate signal interference thatcan be caused by the continuous searching for other D2D devices on theradio bands. Another advantage of targeted network-assisted devicediscovery can be to increase the efficiency of the communicationsnetwork by performing targeted proximity detection at selected dates orlocation and/or for selected UEs. Another advantage of targetednetwork-assisted device discovery can be to decrease power consumptionby decreasing the time a UE, eNode B, or EPC searches for other D2Ddevices.

FIG. 4 shows a data sequence 400 for establishing a network-assisted D2Dcommunications connection between UE A 402 and another UE, such as UE B404, when the other UE is in proximity to UE A. In FIG. 4, UE A 402 cansend intermittent location updates 410 to the EPC 406 and UE B 404 cansend intermittent location updates 412 to the EPC 406. The locationupdates can enable the EPC 406 to be informed of the current locationsof UE A 402 and UE B 404, respectively. In one example, informationcommunicated in the location updates can include a position associatedwith a network coverage area, a position associated with a broadergeographic area of the UE, or a specific determined geographicalposition. In another example, the location updates include informationrelated to a portion of the communication network, such as a node orcell, that the UE is in communication with.

The EPC 406 can receive a proximity detection request 414 from UE A 402requesting to set up D2D communication with one or more other UEs, suchas UE B 404. The proximity detection request 414 can include a windowlength period for defining a length of time during which the UE A 402requests proximity detection. In one embodiment, the proximity detectionrequest 414 can include a window parameter that is a single eventrequest. For example, UE A 402 can request that the EPC 406 make asingle attempt to set up D2D communication between UE A 402 and UE B 404within a length of time.

In another embodiment, the proximity detection request 414 can include awindow parameter that is a time period request. For example, UE A 402can make a request to EPC 406 to continuously, semi-continuously, orperiodically attempt to set up D2D communications between UE A 402 andUE B 404 for a selected length of time.

In one embodiment, when the selected length of time specified in theproximity detection request 414 lapses, the EPC 406 can stop monitoringthe proximity of UE B 404 relative to UE A 402. In one embodiment, theproximity detection request 414 can be issued for multiple UEs. In oneembodiment, the proximity detection request 414 can indicate a requestby UE A 402 for the EPC 406 to indicate when a specific UE (such as UE B404), a type of UE, or a group of UEs is in proximity to UE A 402. Inanother embodiment, the proximity detection request 414 can indicate arequest by UE A 402 to receive assistance from the communicationsnetwork in the D2D UE discovery process.

The EPC 406 can determine at step 416 when the UE A 402 is in proximityof other UEs listed in the proximity detection request 414. In oneexample, the EPC 406 can use information received in one or more UElocation updates 410 or 412 to determine proximity. In another example,the EPC can determine the proximity of UE A 402 relative to UE B 404when UE A 402 and UE B 404 are associated with the same eNode B, are incommunication with selected eNode Bs, or are in communication withselected network elements or subsystems.

When proximity is determined, EPC 406 can communicate a proximityapproval request 418 to UE B 404, requesting to establish a D2Dconnection between UE A 402 and UE B 404. When UE B 404 acceptsproximity approval request 418, the UE B 404 can communicate a proximityapproval acknowledgement (ACK) 420.

When the EPC receives the proximity approval ACK 420, the EPC 406 cantransmit a proximity alert message 422 to UE A 402. The proximity alertmessage 422 can include identifying information of UE B 404 to enable UEA 402 to find and connect with UE B 404. In one embodiment, the D2Dupdate response can include information related to a common discoveryperiod to coordinate discovery timing.

In one embodiment, the EPC 406 can provide a timing or discovery periodin the proximity alert message 422 to establish the D2D communicationslink. UE A 402 can use the proximity alert message 422 from the EPC 406to transmit a discovery message 424 to the other UEs, such as UE B 404,to establish a D2D communications link 426 using the assistanceinformation for the other UEs. During the timing or discovery period, UEA and UE B can attempt to discover each other and establish a D2Dcommunications link using the identification information. Theidentification information can be provided by the EPC 406 to UE B in theD2D Connection Request and to UE A in the D2D Update Response 420.

FIG. 5 shows a data sequence 500 for detecting proximity between UE A502 and another UE, such as UE B 504, based on a proximity detectionrequest. The EPC 506 can receive a proximity detection request 514 fromUE A 502 requesting to set up D2D communications between UE A 502 andone or more other UEs, such as UE B 504. In one embodiment, theproximity detection request 514 can include a date window parameter or alocation window parameter. In one embodiment, the date window parametercan include date window information such as a time of the day or a dayof a week for establishing D2D communications in a communicationsnetwork. In another embodiment, the date window parameter can includedate range window information such as a week of a month or a month of ayear for establishing D2D communications in a communications network.

In one embodiment, the proximity detection request 514 can include awindow parameter that is a single event request. For example, UE A 502can request that the EPC 506 make a single attempt to set up a D2Dcommunications link between UE A 502 and UE B 504 when a selected dateis reached. In another embodiment, the proximity detection request 514can include a window parameter that is a date request. For example, UE A502 can make a request to EPC 506 to continuously, semi-continuously, orperiodically attempt to set up a D2D communications link between UE A502 and UE B 504 beginning at a selected date or date range, such asbeginning at a time of day on a selected day each week.

In one embodiment, when the selected date or date range lapses, the EPC506 may stop monitoring the proximity of UE B 504 relative to UE A 502.In one embodiment, the proximity detection request 514 can be issued formultiple UEs. In one embodiment, the proximity detection request 514 canindicate a request by UE A 502 to the EPC 506 to indicate when aspecific UE (such as UE B 504), a type of UE, or a group of UEs iswithin a selected proximity range of UE A 502 on a selected date orwithin a selected date range. The EPC 506 can determine at step 516 whenthe UE A 502 is in proximity to one or more other UEs listed in theproximity detection request 514.

In another embodiment, the proximity detection request 514 can include alocation window parameter. In one embodiment, the location windowparameter can include location window information such as a selectedgeographic setting for establishing D2D communications in a D2D network.

In one embodiment, the selected geographic setting can include: aselected location type; current location information of a first UE;current location information of a second UE; a selected commercialenvironment setting; a radius setting for a selected radius adjacent thefirst UE; a radius setting for a selected radius adjacent the second UE;a selected state of a country setting; a selected city of a statesetting; a selected region or area setting; a selected landmark setting;a selected landmark type setting; a type of neighborhood setting; aselected location of a structure setting; a location boundary setting;point of reference setting; or a radius setting for a radius surroundinga point of reference.

The EPC 506 can determine at step 516 when the UE A 502 is in proximityof other UEs listed in the proximity detection request 514. In oneexample, the EPC 506 can use information received in one or more UElocation updates 510 or 512 to determine proximity. In another example,the EPC can determine the proximity of UE A 502 relative to UE B 504when UE A 502 and UE B 504 are associated with the same eNode B, are incommunication with selected eNode Bs, or are in communication withselected network subsystems.

When proximity is determined, EPC 506 can communicate a proximityapproval request 518 to UE B 504, requesting to establish a D2Dconnection between UE A 502 and UE B 504. When UE B 504 acceptsproximity approval request 518, the UE B 504 can communicate a proximityapproval acknowledgement (ACK) 520.

In one embodiment, when the EPC receives the proximity approval ACK 520,the EPC 506 can transmit a proximity alert message 522 to UE A 502. Inone embodiment, the proximity alert message 522 can include identifyinginformation of UE B 504 to enable UE A 502 to find and connect with UE B504. In another embodiment, the D2D update response can includeinformation related to a common discovery period to coordinate discoverytiming. In one embodiment, the EPC 506 can provide a timing or discoveryperiod in the proximity alert message 522 to establish the D2Dcommunications link.

In another embodiment, when the EPC receives the proximity approval ACK520, the EPC 506 can transmit a proximity alert message 522 to UE A 502.In one embodiment, the proximity alert message 522 can includeidentifying information of UE B 504 to indicate to UE A 502 when UE B504 is within a selected proximity threshold at a selected locationbased on the location window parameter and/or at a selected date basedon the date window parameter.

FIG. 6 shows a data sequence 600 for establishing a network-assisted D2Dcommunications connection between UE A 602 and another UE, such as UE B604, when a date window parameter occurs. The EPC 606 can receive aproximity detection request 614 from UE A 602 requesting to set up D2Dcommunications between UE A 602 and one or more other UEs, such as UE B604. In one embodiment, the proximity detection request 614 can includea date window parameter. In one embodiment, the date window parametercan include date window information such as a time of the day or a dayof a week for establishing D2D communications in a communicationsnetwork. In another embodiment, the date window parameter can includedate range window information such as a week of a month or a month of ayear for establishing D2D communications in a communications network.

In one embodiment, the proximity detection request 614 can include awindow parameter that is a single event request. For example, UE A 602can request that the EPC 606 make a single attempt to set up a D2Dcommunications link between UE A 602 and UE B 604 when a selected dateis reached. In another embodiment, the proximity detection request 614can include a window parameter that is a date request. For example, UE A602 can make a request to EPC 606 to continuously, semi-continuously, orperiodically attempt to set up a D2D communications link between UE A602 and UE B 604 beginning at a selected date or date range, such asbeginning at a time of day on a selected day each week.

In one embodiment, when the selected date or date range lapses, the EPC606 may stop monitoring the proximity of UE B 604 relative to UE A 602.In one embodiment, the proximity detection request 614 can be issued formultiple UEs. In one embodiment, the proximity detection request 614 canindicate a request by UE A 602 to the EPC 606 to indicate when aspecific UE (such as UE B 604), a type of UE, or a group of UEs iswithin a selected proximity range of UE A 602 on a selected date orwithin a selected date range. The EPC 606 can determine at step 616 whenthe UE A 602 is in proximity to one or more other UEs listed in theproximity detection request 614. The remainder of FIG. 6 issubstantially similar to FIG. 4.

FIG. 7 shows a data sequence 700 for establishing a network-assisted D2Dcommunications connection between UE A 702 and another UE, such as UE B704, when a location window parameter occurs. The EPC 706 can receive aproximity detection request 714 from UE A 702 requesting to set up D2Dcommunicates with an other UE(s), such as UE B 704. In one embodiment,the proximity detection request 714 can include a location windowparameter. In one embodiment, the location window parameter can includelocation window information such as a selected geographic setting forestablishing D2D communications in a D2D network.

In one embodiment, the selected geographic setting can include: aselected location type; current location information of a first UE;current location information of a second UE; a selected commercialenvironment setting; a radius setting for a selected radius adjacent thefirst UE; a radius setting for a selected radius adjacent the second UE;a selected state of a country setting; a selected city of a statesetting; a selected region or area setting; a selected landmark setting;a selected landmark type setting; a type of neighborhood setting; aselected location of a structure setting; a location boundary setting;point of reference setting; or a radius setting for a radius surroundinga point of reference.

In one embodiment, the proximity detection request 714 can include awindow parameter that is a single event request. For example, UE A 702can request that the EPC 706 make a single attempt to set up D2Dcommunicates between UE A 702 and UE B 704 when a selected geographicsetting is reached by UE A 702. In another embodiment, the proximitydetection request 714 can include a window parameter that is a locationrequest. For example, UE A 702 can make a request to EPC 706 tocontinuously, semi-continuously, or periodically attempt to set up a D2Dcommunications link between UE A 702 and UE B 704 when a selectedgeographic setting is reached.

In one embodiment, when the selected geographic setting is reached, theEPC 706 may stop monitoring the proximity of UE B 704 relative to UE A702. In one embodiment, the proximity detection request 714 can beissued for multiple UEs. In one embodiment, the proximity detectionrequest 714 can indicate a request by UE A 702 to the EPC 706 toindicate when a specific UE (such as UE B 704), a type of UE, or a groupof UEs is within a selected proximity range of the UE A 702 at aselected geographic setting. The EPC 706 can determine at step 716 whenUE A 702 is in proximity to one or more other UEs listed in theproximity detection request 714. The remainder of FIG. 7 issubstantially similar to FIGS. 4 and 6.

One advantage of using the location window parameter to determine whento perform proximity detection is that setting up a D2D communicationslink is more efficient when a UE is able to request network-assisteddevice discovery for certain UEs whenever it is in a given location. Forexample, the UE can specify GPS coordinates and a radius of interest forperforming proximity detection. In another example, the UE can specify acurrent location of the UE and a radius of interest for performingproximity detection. In one embodiment, the communications network canperform location estimation on the UE at the current location of the UEto determine the current location of the UE before storing the currentlocation information for a proximity detection procedure. In oneembodiment, the UE can send the EPC a detection window request based onboth a time parameter and a location parameter.

FIG. 8 uses a flow chart 800 to illustrate the functionality of oneembodiment of the computer circuitry with a UE operable to communicatein a D2D network. The functionality may be implemented as a method orthe functionality may be executed as instructions on a machine, wherethe instructions are included on at least one computer readable mediumor one non-transitory machine readable storage medium. The computercircuitry can be configured to communicate, to an evolved packet core(EPC), a proximity detection request, as in block 810. In oneembodiment, the proximity detection request includes a date windowparameter, an identification information of a second UE, and/or aproximity detection signal indicating whether the proximity detectionrequest is for proximity detection of the second UE or for establishinga D2D connection with the second UE. The computer circuitry can befurther configured to receive, from the EPC, a proximity alert messageat a selected date based on the date window parameter, as in block 820.

In one embodiment, the proximity alert message can include assistanceinformation for D2D communication of the UE with the second UE. Inanother embodiment, the computer circuitry can be further configured totransmit, to the second UE, a discovery message to establish a D2Dconnection using the assistance information for the second UE. Inanother embodiment, the date window parameter includes a time of day, aday of a week, a week of a month, or a month of a year for establishingcommunications with the second UE in the D2D network. In anotherembodiment, the proximity detection request includes a location windowparameter. In another embodiment, the location window parameter is aselected geographic setting.

In one embodiment, the selected geographic setting includes a selectedlocation type, a current location information of the first UE, a currentlocation information of the second UE, a selected commercial environmentsetting, a radius setting for a selected radius adjacent the first UE, aradius setting for a selected radius adjacent the second UE, a selectedstate setting, a selected city setting, a selected region setting, aselected landmark setting, a selected landmark type setting, a type ofneighborhood setting, a selected location of a structure setting, alocation boundary setting, point of reference setting, or a radiussetting for a radius surrounding a point of reference.

In another embodiment, the proximity detection request includesidentification information for a plurality of UEs, one or more selectedtypes of UEs, one or more selected groups of UEs, or one or moreselected categories of UEs. In another embodiment, the date windowparameter includes a plurality of times of day, days of a week, weeks ofa month, or months of a year for proximity detection of other UEs in theD2D network or for establishing D2D communications between the UE andother UEs in the D2D network. In another embodiment, the computercircuitry can be further configured to directly communicate with thesecond UE using a D2D communications connection. In another embodiment,the D2D communications connection is a wireless local area network(WLAN) connection, a wireless fidelity (WiFi) direct connection, aBluetooth connection, or a Zigbee connection.

FIG. 9 provides a flow chart 900 to illustrate the functionality of oneembodiment of the computer circuitry with an EPC operable to assist a UEto communicate in a D2D network. The functionality may be implemented asa method or the functionality may be executed as instructions on amachine, where the instructions are included on at least one computerreadable medium or one non-transitory machine readable storage medium.The computer circuitry can be configured to perform a proximitydetection for a first UE and a second UE based on a window parameter ofa proximity detection request from the first UE, as in block 910. Thecomputer circuitry can be further configured to communicate a proximitydetection approval request to the second UE during the window parameter,wherein the proximity detection approval request includes identificationinformation for the first UE, as in block 920. The computer circuitrycan also be configured to receive, from the second UE, a proximitydetection approval response, as in block 930. The computer circuitry canalso be configured to communicate, to the first UE, a proximity alertmessage, as in block 940.

In one embodiment, the proximity detection approval request includestiming information for performing discovery of the first UE. In anotherembodiment, the proximity alert message includes connection informationfor the second UE and timing information for performing discovery of thesecond UE. In another embodiment, the computer circuitry can be furtherconfigured to receive, from the first UE, the proximity detectionrequest, wherein the proximity detection request includes a windowparameter, identification information related to the second UE, and aproximity detection signal indicating whether the proximity detectionrequest is for proximity detection of the second UE or for establishinga D2D connection between the first UE and the second UE.

In one embodiment, the computer circuitry can be further configured tostore a predetermined proximity detection request, wherein thepredetermined proximity detection request includes a window parameterand identification information related to the second UE. In anotherembodiment, the window parameter includes a date window parameter or alocation window parameter. In another embodiment, the computer circuitrycan be further configured to receive location information for the firstUE to determine when the first UE is within the location windowparameter to perform the proximity detection.

In another embodiment, the computer circuitry can be further configuredto determine a location of the first UE or the second UE using a globalposition system (GPS), signal triangulation, a beacon signal, cellcoverage based positioning, observed time difference of arrival (OTDOA)positioning, enhanced observed time difference (E-OTD) positioning,assisted-global navigation satellite system (A-GNSS) positioning, uplinktime difference of arrival (UTDOA) positioning, or enhanced observedtime difference (E-OTD) positioning. In another embodiment, the computercircuitry is further configured to provide the first UE with windowparameter selection options. In another embodiment, the computercircuitry can be further configured to monitoring, in substantiallyreal-time, when the second UE is within a selected radius of the firstUE.

FIG. 10 uses a flow chart 1000 to illustrate the functionality of oneembodiment of a method for assisting a UE to communicate in a D2Dnetwork. The method can comprise communicating, to an EPC, a proximitydetection request, as in block 1010. In one embodiment, the proximitydetection request can include a location window parameter, anidentification information of a second UE, and/or a detection signalindicating whether the proximity detection request is for proximitydetection of the second UE or for establishing a D2D connection with thesecond UE. The method can further comprise receiving, from the EPC, aproximity alert message at a selected date based on the location windowparameter, as in block 1020.

In one embodiment, the method can further comprise transmitting, to thesecond UE, a discovery message to establish a D2D connection using theassistance information for the second UE. In another embodiment, theproximity detection request includes a date window parameter. In anotherembodiment, the location window parameter or the date window parameteris a recurring event. In another embodiment, the method can furthercomprise communicating, to the EPC, a proximity detection cancellationrequest, wherein the proximity detection cancellation request stops theEPC from determining when a proximity event occurs based on theproximity detection request when the UE is located within the locationwindow parameter or the date window parameter. In another embodiment,the method can further comprise receiving, at the first UE, proximitydetection request information from user input information.

FIG. 11 provides an example illustration of the wireless device, such asa user equipment (UE), a mobile station (MS), a mobile wireless device,a mobile communication device, a tablet, a handset, or other type ofwireless device. The wireless device can include one or more antennasconfigured to communicate with a node or transmission station, such as abase station (BS), an evolved Node B (eNB), a baseband unit (BBU), aremote radio head (RRH), a remote radio equipment (RRE), a relay station(RS), a radio equipment (RE), a remote radio unit (RRU), a centralprocessing module (CPM), or other type of wireless wide area network(WWAN) access point. The wireless device can be configured tocommunicate using at least one wireless communication standard including3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and Wi-Fi.The wireless device can communicate using separate antennas for eachwireless communication standard or shared antennas for multiple wirelesscommunication standards. The wireless device can communicate in awireless local area network (WLAN), a wireless personal area network(WPAN), and/or a WWAN.

FIG. 11 also provides an illustration of a microphone and one or morespeakers that can be used for audio input and output from the wirelessdevice. The display screen may be a liquid crystal display (LCD) screen,or other type of display screen such as an organic light emitting diode(OLED) display. The display screen can be configured as a touch screen.The touch screen may use capacitive, resistive, or another type of touchscreen technology. An application processor and a graphics processor canbe coupled to internal memory to provide processing and displaycapabilities. A non-volatile memory port can also be used to providedata input/output options to a user. The non-volatile memory port mayalso be used to expand the memory capabilities of the wireless device. Akeyboard may be integrated with the wireless device or wirelesslyconnected to the wireless device to provide additional user input. Avirtual keyboard may also be provided using the touch screen.

Various techniques, or certain aspects or portions thereof, may take theform of program code (i.e., instructions) embodied in tangible media,such as floppy diskettes, CD-ROMs, hard drives, non-transitory computerreadable storage medium, or any other machine-readable storage mediumwherein, when the program code is loaded into and executed by a machine,such as a computer, the machine becomes an apparatus for practicing thevarious techniques. In the case of program code execution onprogrammable computers, the computing device may include a processor, astorage medium readable by the processor (including volatile andnon-volatile memory and/or storage elements), at least one input device,and at least one output device. The volatile and non-volatile memoryand/or storage elements may be a RAM, EPROM, flash drive, optical drive,magnetic hard drive, or other medium for storing electronic data. Thebase station and mobile station may also include a transceiver module, acounter module, a processing module, and/or a clock module or timermodule. One or more programs that may implement or utilize the varioustechniques described herein may use an application programming interface(API), reusable controls, and the like. Such programs may be implementedin a high level procedural or object oriented programming language tocommunicate with a computer system. However, the program(s) may beimplemented in assembly or machine language, if desired. In any case,the language may be a compiled or interpreted language, and combinedwith hardware implementations.

It should be understood that many of the functional units described inthis specification have been labeled as modules, in order to moreparticularly emphasize their implementation independence. For example, amodule may be implemented as a hardware circuit comprising custom VLSIcircuits or gate arrays, off-the-shelf semiconductors such as logicchips, transistors, or other discrete components. A module may also beimplemented in programmable hardware devices such as field programmablegate arrays, programmable array logic, programmable logic devices or thelike.

Modules may also be implemented in software for execution by varioustypes of processors. An identified module of executable code may, forinstance, comprise one or more physical or logical blocks of computerinstructions, which may, for instance, be organized as an object,procedure, or function. Nevertheless, the executables of an identifiedmodule need not be physically located together, but may comprisedisparate instructions stored in different locations which, when joinedlogically together, comprise the module and achieve the stated purposefor the module.

Indeed, a module of executable code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different storage devices, and may exist, atleast partially, merely as electronic signals on a system or network.The modules may be passive or active, including agents operable toperform desired functions.

Reference throughout this specification to “an example” means that aparticular feature, structure, or characteristic described in connectionwith the example is included in at least one embodiment of the presentinvention. Thus, appearances of the phrases “in an example” in variousplaces throughout this specification are not necessarily all referringto the same embodiment.

As used herein, a plurality of items, structural elements, compositionalelements, and/or materials may be presented in a common list forconvenience. However, these lists should be construed as though eachmember of the list is individually identified as a separate and uniquemember. Thus, no individual member of such list should be construed as ade facto equivalent of any other member of the same list solely based ontheir presentation in a common group without indications to thecontrary. In addition, various embodiments and example of the presentinvention may be referred to herein along with alternatives for thevarious components thereof. It is understood that such embodiments,examples, and alternatives are not to be construed as defactoequivalents of one another, but are to be considered as separate andautonomous representations of the present invention.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided, such asexamples of layouts, distances, network examples, etc., to provide athorough understanding of embodiments of the invention. One skilled inthe relevant art will recognize, however, that the invention can bepracticed without one or more of the specific details, or with othermethods, components, layouts, etc. In other instances, well-knownstructures, materials, or operations are not shown or described indetail to avoid obscuring aspects of the invention.

While the forgoing examples are illustrative of the principles of thepresent invention in one or more particular applications, it will beapparent to those of ordinary skill in the art that numerousmodifications in form, usage and details of implementation can be madewithout the exercise of inventive faculty, and without departing fromthe principles and concepts of the invention. Accordingly, it is notintended that the invention be limited, except as by the claims setforth below.

The invention claimed is:
 1. A user equipment (UE) operable tocommunicate in a peer to peer (P2P) network, the UE having one or moreprocessors configured to: communicate, to a proximity services (ProSe)server in an Evolved Packet Core (EPC), a proximity detection request,wherein the proximity detection request includes: a time period windowparameter; an identification information of a second UE, and a proximitydetection signal indicating whether the proximity detection request isfor proximity detection of the second UE or for establishing a P2Pconnection with the second UE; and identifying that a proximity alertmessage, received from the ProSe server, is received within a timeperiod of the time period window parameter.
 2. The UE of claim 1,wherein the proximity alert message include assistance information forP2P communication of the UE with the second UE.
 3. The UE of claim 2,wherein the one or more processors are further configured to transmit,to the second UE, a discovery message to establish a P2P connectionusing the assistance information for the second UE.
 4. The UE of claim1, wherein the time period window parameter includes a time of day, aday of a week, a week of a month, or a month of a year for establishingcommunications with the second UE in the P2P network.
 5. The UE of claim1, wherein the proximity detection request includes a location windowparameter, wherein the location window parameter is a selectedgeographic setting.
 6. The UE of claim 1, wherein the time period windowparameter includes a plurality of times of day, days of a week, weeks ofa month, or months of a year for proximity detection of other UEs in theP2P network or for establishing P2P communications between the UE andother UEs in the P2P network.
 7. The UE of claim 1, wherein the one ormore processors are further configured to directly communicate with thesecond UE using a P2P communications connection.
 8. The UE of claim 7,wherein the P2P communications connection is a wireless local areanetwork (WLAN) connection.
 9. The UE of claim 1, wherein the UE includesan antenna, a touch sensitive display screen, a speaker, a microphone, agraphics processor, an application processor, an internal memory, or anon-volatile memory port.
 10. A non-transitory machine readable storagemedium having instructions embodied thereon, the instructions beingexecuted by one or more processors to perform the following operations:generating, at a first user equipment (UE), a proximity detectionrequest to be communicated to a proximity services (ProSe) server,wherein the proximity detection request includes: a time period windowparameter; an identification information of a second UE, and a proximitydetection signal indicating whether the proximity detection request isfor proximity detection of the second UE or for establishing a P2Pconnection with the second UE; and identifying that a proximity alertmessage, received from the ProSe server, is received within a timeperiod of the time period window parameter.
 11. The non-transitorymachine readable storage medium of claim 10, wherein the proximity alertmessage include assistance information for P2P communication of thefirst UE with the second UE.
 12. The non-transitory machine readablestorage medium of claim 10, further comprising instructions which whenexecuted by the one or more processors perform the following operation:configuring a discovery message for transmission from the first UE tothe second UE to establish a P2P connection using the assistanceinformation for the second UE.
 13. The non-transitory machine readablestorage medium of claim 10, wherein the time period window parameterincludes a time of day, a day of a week, a week of a month, or a monthof a year for establishing communications with the second UE in the P2Pnetwork.
 14. The non-transitory machine readable storage medium of claim10, further comprising instructions which when executed by the one ormore processors perform the following operation: directly communicatewith the second UE using a P2P communications connection.
 15. Thenon-transitory machine readable storage medium of claim 10, wherein theP2P communications connection is a wireless local area network (WLAN)connection.
 16. A method for communicating in a peer to peer (P2P)network, the method comprising: communicating, from a user equipment(UE) to a proximity services (ProSe) server in an Evolved Packet Core(EPC), a proximity detection request, wherein the proximity detectionrequest includes: a time period window parameter; an identificationinformation of a second UE, and a proximity detection signal indicatingwhether the proximity detection request is for proximity detection ofthe second UE or for establishing a P2P connection with the second UE;and receiving, at the UE from the ProSe server, a proximity alertmessage at a selected time based on the time period window parameter.17. The method of claim 16, further comprising transmitting, from thefirst UE to the second UE, a discovery message to establish a P2Pconnection using the assistance information for the second UE.
 18. Themethod of claim 16, wherein the UE directly communicates with the secondUE using a P2P communications connection, wherein the P2P communicationsconnection is a wireless local area network (WLAN) connection.
 19. Themethod of claim 16, wherein the time period window parameter includes aplurality of times of day, days of a week, weeks of a month, or monthsof a year for proximity detection of other UEs in the P2P network or forestablishing P2P communications between the UE and other UEs in the P2Pnetwork.
 20. The method of claim 16, wherein the proximity detectionrequest includes a location window parameter, wherein the locationwindow parameter is a selected geographic setting.
 21. A proximityservices (ProSe) server operable to communicate in a peer to peer (P2P)network, the ProSe server having one or more processors configured to:receive, from a user equipment (UE), a proximity detection request,wherein the proximity detection request includes: a time period windowparameter; an identification information of a second UE, and a proximitydetection signal indicating whether the proximity detection request isfor proximity detection of the second UE or for establishing a P2Pconnection with the second UE; and send a proximity alert message to theUE within a time period based on the time period window parameter. 22.The ProSe server of claim 21, wherein the ProSe server operates in anEvolved Packet Core (EPC).
 23. The ProSe server of claim 21, wherein thetime period window parameter includes a time of day, a day of a week, aweek of a month, or a month of a year for establishing communicationswith the second UE in the P2P network.
 24. The ProSe server of claim 21,wherein the proximity detection request includes a location windowparameter, wherein the location window parameter is a selectedgeographic setting.